Q: Why does BuildDisk tell me “permission denied” and die? Doesn't it run as root?\
\
A: One cause of this is related to running BuildDisk while your machine is connected to the network. BuildDisk tries to ensure that what it's building will fit on the target disk. To do this, it calculates the size of each directory to be loaded. If, for example, you have
\b /NextDeveloper/Example
\b0 imported from an NFS server, and if there's a
\b .NextTrash
\b0 directory in that directory, the
\b root
\b0 user might not be able to see what's inside in order to determine the size.\
\
Whenever possible, run BuildDisk on a system that's
\i disconnected
\i0 from the network.\
\
If you
\i must
\i0 be connected to the network (e.g., if you're running BuildDisk on a NeXTstation that's NetBooted), and if you get a message like the above, go to the machine that's serving the flagged directory and remove the
\b .NextTrash
\b0 directory and its subdirectories (or whatever other directory is giving you problems). If removing the directory is inappropriate, either grant everyone read permission, or export the file system (through
\b exportfs
\b0 and the
\b /etc/exports
\b0 file; see the UNIX Manal Pages or the
\i NeXT Network and System Administration
\i0 manual) to grant root access as necessary to the NetBoot client.\
\
It's also possible that you'll run out of space on the target machine if you're importing large directories from an NFS server.\